Configure Puppeteer executablePath chrome in your local Windows

Question

• Puppeteer version : 1.11.0
• Platform / OS version: Windows 10 pro
• Node.js version: 12.6.6

When I did a local development test in windows, happen was problem in executablePath.

"Failed to launch chrome! spawn /usr/bin/chromium-browser ENOENT"

I saw for windows needs to get complete path. Otherwise cannot find chrome.exe

Default in code:

const browser = await puppeteer.launch({executablePath: '/path/to/Chrome'});

In windows it worked thus:

const browser = await puppeteer.launch({executablePath: 'C:\\your_workspace\\node_modules\\puppeteer\\.local-chromium\\win64-(version)\\chrome-win\\chrome.exe'});

In visual code suggest the path

Visual Code view explorer

Answer 1

You can also set the environment variable PUPPETEER_EXECUTABLE_PATH.

This is useful in conjunction with PUPPETEER_SKIP_CHROMIUM_DOWNLOAD set to true

Answer 2

Maybe this can help:

const osPlatform = os.platform(); // possible values are: 'darwin', 'freebsd', 'linux', 'sunos' or 'win32'
console.log('Scraper running on platform: ', osPlatform);
let executablePath;
if (/^win/i.test(osPlatform)) {
  executablePath = '';
} else if (/^linux/i.test(osPlatform)) {
  executablePath = '/usr/bin/google-chrome';
}

Answer 3

This was the fix for me on Alpine trying to get a Dockerfile to work.

Relevant bit from Dockerfile:

RUN apk add --update chromium

Relevant bit from config (copied inside the image in project root)

/**
 * @type {import("puppeteer").Configuration}
 */
module.exports = {
    executablePath: '/usr/bin/chromium',
    cacheDirectory: '/var/www/html/.cache/puppeteer', # See footnote
};

* This was needed for my build. I believe this isnt an issue if you're not doing that, but maybe it can save someone some time.
The error it fixed was Could not find Chrome (ver. 119.[...]). This can occur if either [...]